System and method for quality control, inspection and audit of utility assets

ABSTRACT

Method for capturing, organizing and retrieving data for utility assets using RFID tags, including: storing data related to a plurality of utility assets in a database, wherein the stored data include data about type of the utility asset; repair, documentation, testing validation, and inspection of the utility asset; programming a plurality of RFID tags for placement on a utility asset, by one or more processors; placing the programmed RFID tags on the utility asset; linking stored data related to the utility asset with the programmed data for the placed RFID tags, including location data of the placed RFID tags; and querying one or more of the placed RFID tags to retrieve data about the utility asset including data about the location of the utility asset, the specific segment and the specific joint, the type of the utility asset; repair, documentation, testing validation, and inspection of the utility asset, by one or more processors.

CROSS-REFERENCE TO RELATED APPLICATIONS

This Patent Application claims the benefits of U.S. Provisional PatentApplication Ser. No. 61/652,781, filed on May 29, 2012 and entitled“System And Method For Quality Control, Inspection And Audit Of UtilityAssets,” the entire contents of which are hereby expressly incorporatedby reference.

FIELD OF THE INVENTION

The present invention relates generally to computer software; and moreparticularly to system and method for quality control, inspection andaudit of utility assets (QCIA).

BACKGROUND

There are many assets above ground and below ground that need to beprotected and avoided. Included in these assets are utility lines andcomponents and protected areas, such as archeological sites and habitatof endangered species. There are millions of miles of utility linesaround the world, some buried and some above ground. These utility linesinclude, without limitation, electric power lines, telephone lines,water lines, sewer lines, fiber-optic cable lines, natural gastransmission lines, natural gas distribution lines, and utility linesfor transporting hazardous liquids.

Every year incidents occur in which mobile ground breaking equipmentcomes in contact with utility lines with costly results in loss of lifeand/or loss of money. In order to understand the full impact of suchincidents, one would have to also include environmental damage andeconomic loss as a result of a service disruption.

There have been many attempts to address damage prevention whengroundbreaking equipment is used around utilities and other assets thatneed protection. Non-exhaustive examples of these attempts includemarking the location of a utility by painted lines. Commonly in thepast, the utility companies and/or service companies are called to thesite to place marks (spray the ground with an identifying color; forexample, red for electric lines, yellow for gas lines and so forth) onthe surface to show the location of a specific utility line and/or itscomponents. However, such marking is not permanent and typically lastsonly for the one earth moving operation, such as digging a trench, forwhich the utilities were marked.

Another approach was to make a record of the location of the utilitylines as the line was placed in the earth. However, the accuracy of thelocation is dictated by the accuracy of the reference point. It has beenfound that attempting to locate a utility line based on this record hasresulted in an error of up to 15 feet or more because of the inaccuracyin the position of the reference point.

Accordingly, there is a need for a system and method for qualitycontrol, inspection and audit of utility assets.

SUMMARY

In some embodiments, the present invention is computer implementedmethod for capturing, organizing and retrieving data for utility assetsusing RFID tags. The method includes: storing data related to aplurality of utility assets in a database, wherein the stored datainclude data about type of the utility asset; repair, documentation,testing validation, and inspection of the utility asset; programming aplurality of RFID tags for placement on a utility asset, by one or moreprocessors; placing the programmed RFID tags on the utility asset. Atleast one of the programmed RFID tags may be placed on a specificsegment of the utility asset as a segment tag, and at least one of theprogrammed RFID tags is placed near a specific joint of the utilityasset as a join tag. The method further includes: linking stored datarelated to the utility asset with the programmed data for the placedRFID tags, including location data of the placed RFID tags; and queryingone or more of the placed RFID tags to retrieve data about the utilityasset including data about the location of the utility asset, thespecific segment and the specific joint, the type of the utility asset;repair, documentation, testing validation, and inspection of the utilityasset, by one or more processors.

In some embodiments, the present invention is computer implementedmethod for capturing, organizing and retrieving data for utility assetsusing RFID tags. The method includes: storing data related to aplurality of utility assets in a database, wherein the stored datainclude data about type of the utility asset; repair, documentation,testing validation, and inspection of the utility asset; programming aplurality of RFID tags for placement on a utility asset, by one or moreprocessors. The programming process may further include: retrieving aunique RFID tag identifier from the RFID tag using an RFID readerdevice, linking data associated with the utility asset to the uniqueRFID tag identifier, and checking out the programmed RFID tag from anRFID inventory database. The method further includes: placing theprogrammed RFID tags on the utility asset; linking stored data relatedto the utility asset with the programmed data for the placed RFID tags,including location data of the placed RFID tags; and querying one ormore of the placed RFID tags to retrieve data about the utility assetincluding data about the location of the utility asset, the type of theutility asset, repair, documentation, testing validation, and inspectionof the utility asset, by one or more processors.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an exemplary overview, according to some embodiments of thepresent invention.

FIG. 2 is an exemplary process flow, according to some embodiments ofthe present invention.

FIG. 3 depicts an exemplary method for tag placement of an utilityasset, according to some embodiments of the present invention.

FIG. 4 is an exemplary process flow for the opening and closing of afile or data set of information, according to some embodiment of thepresent invention.

FIG. 5 depicts an exemplary QC_SEGMENT, according to some embodiments ofthe present invention.

FIG. 6 is a representation of various types of QC_SEGMENTS that may bedefined in a normal pipeline scenario, according to some embodiments ofthe present invention.

FIG. 7 shows a read/write process of locating RFID tags that have beenplaced on an INFRA, according to some embodiments of the presentinvention.

FIG. 8 is an exemplary process for reading RFID tags that are buriedunderground, according to some embodiments of the present invention.

FIG. 9 depicts an exemplary process flow for opening tags and closingtags, according to some embodiments of the present invention.

FIG. 10 shows an exemplary DATA_SET record, according to someembodiments of the present invention.

FIG. 11 depicts an exemplary system level architecture, according tosome embodiments of the present invention.

FIG. 12 is an exemplary process flow executed by one or more processors,according to some embodiments of the present invention.

DETAILED DESCRIPTION

The present invention is directed to a system and method for qualitycontrol, inspection and audit of utility assets (QCIA). The inventionprovides a method and system for locating, tracking, measuring, anddocumenting the history of critical components of pipeline architectureand relating these components to tags that can be used for onsitevalidation and location, as required during the life cycle of theutility assets, such as pipeline, and related facilities (INFRA). Someor all of the processes of the invention is executed by one or morecomputers/processors and may include various databases. The inventionassists the over and underground utility assets management forindustries such as the oil and gas industries in achieving PipelineIntegrity Management (PIM). Asset (e.g., pipeline) Integrity managementis achieved when the facility owner has timely access to comprehensivepipeline configuration data that supports the timely, accurate, costeffective operational life cycle management of pipeline and facilitiesto include audit, risk assessments, locating, damage prevention,emergency response, repair, maintenance, modifications, compliance andregulatory.

Moreover, the invention provides a proprietary process for collectingdata and creating an audited data pedigree related to INFRA. Joint andjoin and other critical data associated with build and repair of INFRAis linked by a unique identifier to Radio Frequency Identification(RFID) tags, which are placed on or in close proximity to the associatedfeatures that are being documented.

In some embodiments, the invention incorporates RFID (or transponders),GPS, GIS and other state of the art data management services andsoftware and hardware technology. The invention introduces new processesfor viewing, organizing, collecting, displaying and auditing data andtying or linking this data to facility locations, creating new standardsfor ensuring that PIM is achieved.

In some embodiments, the invention uses an (on-line) database ofpipeline and facilities configuration data that is securely and remotelyaccessed, for example, from the office or the field. The inventionuniquely incorporates the use of RFID technology to tag points andsegments of interest on the pipeline and related facilities in a mannerthat facilitates the audit of key tasks required of the build, repair,inspection, maintenance and validation of the life cycle of the pipelineand related facilities. The invention provides for critical ‘last mile’physical and visual validation of infrastructure status includingvalidation of repairs and maintenance. Additionally, the inventionsupports the full life-cycle documentation of pipelines and relatedinfrastructure, from original engineering data though as-built andbeyond and includes collecting and reporting critical field data relatedto joints, joins and other as-built configurations.

In some embodiments, the invention is utilized for the full spectrum ofpipeline configurations and related facilities used in the oil, gas andutility industries. For example, the invention provides the developmentof audited pipe segment and joint pedigree data sets and an automatedprocess for recalling this data as required for compliance purposes.Furthermore, the invention takes into consideration all permutations ofutility assets (e.g., pipe) types (e.g., metal or plastic) segments.Although for simplicity reasons, the examples about the utility assetsgiven in the present disclosure mainly use a pipeline, one skilled inthe art would recognize that the present invention is not limited topipelines and thus other utility assets, such as electrical lines, phonelines, sewage lines and other assets are within the scope of the presentinvention.

In some embodiments, the invention supports the gathering of pipelinerelated data and linking this data with field installed RFID tags(TAGs). TAGs are installed in key locations both above and below groundand on and around pipelines and associated facilities locations. TAGsare unique identifiers and can be queried directly for data that isstored in the TAGs. The invention links TAGs to data that provideshighly accurate GPS (X, Y) locations of the TAGs including depth (X, Y,and Z) as well as relevant data associated with the TAGs. GPS dataallows for determining approximate locations of buried TAGs, thusallowing for further direct query and linking both above and belowground.

According to some embodiments of the invention, RFID tags (TAGs) ofactive or passive design, are attached to pipeline and facilities bothabove and below ground and are readable both above and below ground withnew future technologies. The invention also includes a new concept foran RFID reader capable of reading TAGs below ground and the concept thatthese TAGs utilize attached sensors (TAG_SENSOR) of both passive oractive design (utilizing external power sources like batteries) andprovide location and data validation as well as sensor readings bothabove and below ground.

Field workers can query both above ground and below ground TAGs and beautomatically connected to applicable configuration and compliance dataassociated with the TAGs. TAGs are initially installed when INFRA isbuilt or when INFRA is exposed for various (repair or inspection) or anyother reason during its lifecycle. The combination of field installedTAGs combined with life cycle pipeline configuration management of datafacilitates provides a powerful suite of quality control, riskassessment, damage prevention and compliance services for facilityowners and their service companies. Information in the form of apipeline open data standard (POD), compliant, and/or geospatiallyenabled data set (DATA_SET) assist professionals with responsibilitiesin damage prevention and management of assets to make better businessand operational decisions. PODS provides pipeline operators scalabledatabase architecture to integrate critical records and analysis datawith geospatial location for each component of the pipeline system in avendor-neutral platform.

Through the use of this information, utility owners will be able tobetter track their assets and also reduce the likelihood of conflict,damage and resulting losses to their assets that often occur duringconstruction activities.

In some embodiments, the invention is a method and apparatus forcapturing and organizing, archiving, retrieving and tagging and locatingkey information related to the full life-cycle build inspection, testingand repair of oil and gas or other types of pipelines or relatedinfrastructures (INFRA).

In some embodiments, the invention is comprised of a master life cycleprocess or methodology called the QC process (QC_PROCESS) and the datagenerated from this process, taken as a whole, provides a qualitycontrol, inspection and audit data set and documentation baseline(DATA_SET) that can be used for due diligence, maintenance, inspectionand repair activities during and after INFRA is built or repaired. Insome embodiments, DATA_SET creation occurs during the implementation ofQC_PROCESS working under the control of QCIA standards (QC_STANDARDS)and processes called WORK_UNIT, DATA_LIFE and TAG_LIFE and operating ina computing system architecture including one or more computing deviceand is called QC_ARCHITECTURE.

In some embodiments, DATA_LIFE is a method and process that is primarilycomprised of automated processes and business rules that control thegeneration of a complete, secure, Internet accessible DATA_SET ofapplicable build, test, repair, inspection, compliance and project dataassociated with INFRA during construction and afterward for the entireINFRA life cycle.

In some embodiments, DATA_SET is data organized under a unique datamodel that is created and then tied to INFRA points of interest calledQC Reference Points (QC_POINTS) and areas or segments of INFRA called QCSegment (QC_SEGMENT) via the use of different types of RFID tags (TAGs).TAGs are geospatially referenced and are tied back to DATA_SET data viaa unique TAG identifier called (TAG_ID). (TAG_ID) serves the purpose ofidentifying the unique type of TAG (TAG_TYPE) and a unique identifierfor the TAG within the context of each QC_PROCESS and an absolute uniqueidentifier for the tag itself.

In some embodiments, TAG_LIFE controls the life cycle of the managementof TAGs during the QC_PROCESS and is integrated with the DATA_LIFEprocess. TAG_LIFE controls the TAG life cycle of an INFRA project thatis being controlled by the QC_PROCESS and includes initial commissioningof TAGs, tying of tags to DATA_SET data and the rules for placement ofTAGs during the QC_PROCESS. The primary sub process of TAG_LIFE iscalled OPEN_TAG-CLOSE_TAG. This process combines collection of data withthe tagging of INFRA. OPEN_TAG-CLOSE_TAG ensures that the accomplishmentof work (WORK_UNIT), data about the work (DATA_SET) and tagging of INFRAis integrated. OPEN_TAG-CLOSE_TAG provides for the non-linear ornon-sequential commissioning, tie to DATA_SET, placement, and audit ofeach type of TAG thus guaranteeing that the TAG fully supports the QCIAconcept of LAST_MILE validation.

Audit of the collection of data, inspection, completion of tasks andtagging is controlled by an automated QCIA process called WORK_UNIT.WORK_UNIT process divides or parses INFRA related build, test, inspect,and repair tasks into identifiable units of work called WORK_UNITS.WORK_UNITS are a natural grouping (NATURAL-GROUPING) of tasks or actionsand collection of associated data about the task (who, what, when, whereand how) and related audit data about those tasks. WORK_UNITS aredefined based upon criteria and business rules set by the QC_PROCESS andmay be different depending on the application of QC_PROCESS to differenttypes of jobs that affect INFRA.

The QC_PROCESS generates a DATA_SET by gathering data from multiplesources during the life cycle of INFRA and provides the ability to findand locate and validate QC_POINT and QC_SEGMENT of INFRA on location andtie the data and the validation together even years after INFRA has beencompleted or changed ownership and management control multiple times.

FIG. 1 is an exemplary overview of the present invention. In someembodiments, the invention include the following components or methods.Each of the components and methods is comprised of a number of new andunique automated sub-processes.

Block 11 of FIG. 1 is an exemplary conceptual representation of some ofthe functional processes that constitute the QC_Process, according tosome embodiments of the present invention. This block is conceptual onlyand does not represent the complete set of processes of the QC_Process.Each feature module of the QC_PROCESS utilizes and/or operates onexisting or new data and is executed on one or more processors and/orcomputers. The features shown in blocks 12 through 18 are all applicableto each operation that is represented conceptually in block 11. In otherwords, as a feature (e.g., TEST) is being performed (e.g., by aprocessor), the data management, data control, query and reportingfunctions are applied to it, during its life cycle in completing thefeature.

DATA_LIFE 12 and TAG_LIFE 15 are Data and RFID chip management processesand standards that are applied in creating DATA_SET 17. DATA_LIFE 12includes rules and standards for collecting data at different pointsduring the QC_PROCESS 11. TAG_LIFE 15 includes process of managing thelife cycle of TAGs from initial commissioning through installation andgeospatial referencing.

COLLECT DATA 13 represents the varied methods that are used at variouspoints in the QCIA process to collect applicable data at applicabletimes during the QCIA process.

COMMISSION TAGS 14 represent the process that manages RFID tags from aproject inventory standpoint and provides them to the field forimplementation using the TAG_LIFE process. It represents the process ofchecking RFID tags out of inventory and placing the TAGs on theinfrastructure that is being built or repaired. COMMISSION TAGS isdependent on the TAG_LIFE process 15.

TAG_QUERY 16 represents the query of TAGS after they have been placed onthe infrastructure. Query of TAGS can take place at any time during theQC_Process, from the initial reading of TAG unique ID information to thequery of TAGS years after the tags have been placed. TAG_QUERY isclosely tied to and utilizes DATA SET 17 includes the data about theTAG. When a TAG is queried, it uses the unique identifier on the TAG toaccess data about the TAG. The data about the TAG is a part of theDATA_SET 13, which was developed during the COLLECT_DATA function, underthe guidance and standards of the DATA_LIFE process or methodology.

REPORTING 18 represents top level and detailed reports that aregenerated from the DATA_SET 17, for example, based on security rules andstandards. Reporting is generated as required using a variety ofreporting tools and using DATA_SET data as its basis.

FIG. 2 is an exemplary process flow for a QC_PROCESS, according to someembodiments of the present invention. In some embodiments, QC_PROCESSutilizes and incorporates the following modules. PROJECT SETUP ANDADMINISTRATION (ADMIN) 201 is a setup of project level informationincluding facility owners, engineering specs, operators, operatorqualifications etc. ADMIN data is linked to various operational steps asrequired during the build of the system. For example, OperatorQualifications (OQ) data is utilized downstream of the project setupduring the JOIN QC_PROCESS to identify welders doing the actual work ofthe join QC_PROCESS.

COMPONENTS AND UNITS INVENTORY SYSTEM (INVENTORY) 202 is a QC_PROCESS.This module provides for the inventory and provisioning and collectionof relevant specification data related to material used in the buildwhich are pipeline COMPONENTS AND UNITS. In some embodiments, pipe andfittings are unloaded in an area easily accessible for the workers. Thematerial is tagged and inventoried as it is off loaded and sorted intoidentified areas. For example, a QC hand or fitter can request fittings,which are signed out to a spool sheet number. A welder can then jointhem and return the completed sheet to the QC hand or the fitter.

RFID INVENTORY SYSTEM 203 is a data management and inventory control andfield commissioning (COMMISSION) of TAGs and supports TAG_LIFE process.SURFACE FACILITY (FACILITY) 204 is a QC_PROCESS step that supportsdesign, build, testing and inspection of pipeline surface facilities.PIPELINE 205 is also a QC_PROCESS step that supports design, build,testing, installation and inspection of pipeline.

CROSSING 206 is also a QC_PROCESS step that supports definition, build,test and inspection and installation of pipeline crossings. ThisQC_PROCESS step has a tie-in at both ends where the mainline connects tothe drag sections. The new line may cross one or many utilities in thesame crossing. The crossings are numbered. The entry and exits arerecorded as are the tie in welds and crossing information.

TIE-IN 207 is also a QC_PROCESS step that supports definitions oftie-ins and build test and inspection of TIE-IN. This is the QC_PROCESSthat completes the pipeline from the start point to the completionpoint. It may, at times, require a HOT TIE-IN meaning being tied into alive line or facility. Tie-ins may be loose ends left for slack control,risers, underground branch connections, expansion loops or facilitiesabove ground.

REPAIR/INSPECT 208 is also a QC_PROCESS step that supports definitionsof repair and inspection activity and repair and inspection of repairand inspection segments of existing pipelines. This is the QC_PROCESSthat outlines how an existing pipeline that has anomalies is inspectedinternally or directly and repaired. It may be as simple as repairingthe external coating, adding an external sleeve to contain pressure oras complicated as doing a section cut out and replacing the cut out witha piece of pre tested pipe.

PROVISION COMPONENTS 209 provisions the pipeline components frominventory and in doing so provides material information related to theactions taking place on INFRA. For example, provisioning of pipesegments into a JOIN WORK_UNIT include the manufacturer and heat numbersof the pipes. TAG 210 is a WORK_UNIT sub task. COMPONENTS (pipe, valves,flanges) are tagged from an INVENTORY perspective prior to their use inthe field.

JOIN 211 works for a WORK_UNIT. Typically, joining comes after stringingof components. JOIN 211 can be steel or non-steel (plastic). The join istypically tested by NDE and sometimes destructive methods and this datawill be entered via the ADMIN part of the QC_PROCESS. The welders aretested to the procedure required for the type of pipe used. The plastictechnician's first join are also tested, for example, by a destructivemethod. All technician information is documented.

NDE XRAY 212 is a non-destructive X-ray of weld accomplished by JOIN211. XRAY is done by separate X-ray crews and data is added in order toclose the JOIN WORK_UNIT and the TAG that is attached at the JOINQC_POINT. TAG 213 is placed per QC_STANDARD at a QC_POINT upstream ordownstream of the JOIN. TAG references and ties data to a QC_POINTrelated to a JOIN, repair or other action taken on the INFRA. It differsfrom the previous TAG which has material or inventory data emphasis.

QC_SEGMENT 214 is defined to describe the environmental conditions ofthe ditch into which the lower in or install of the pipeline is takingplace. Other QC_SEGMENTs are defined as required to circumscribepressure test areas and other segments of INFRA that may be of interestto inspectors later in the life-cycle of INFRA. LOWER IN 215 installsWORK_UNIT. In some embodiments, the installation QC_PROCESS includesditching, soap testing, sizing pig/gauging (surface) lowering in,holiday testing, coating repair and backfill. It also includes unitinstallations. All operations within this QC_PROCESS are watched andacknowledged by entries into the hand held device.

FIG. 2 represents a reads process flow, according to some embodiments ofthe present invention. The critical path methodology and practices ofthe QC_PROCESS INTERACT with and act as an EXTENSION to standard buildand repair practices in the Oil & Gas Pipeline industry. The QC_PROCESSis APPLIED TO and DURING and IN ADDITION TO, normal pipeline, buildrepair and maintenance activities. FIG. 2 SHOWS AN INTERLEAVED VIEW OFQC_PROCESS FUNCTIONS THAT ARE EITHER NEW OR ARE DIRECTLY APPLIED TONORMAL INFRA BUILD REPAIR AND MAINTENANCE FUNCTIONS. Appendix A of theProvisional Patent Application Ser. No. 61/652,781, the entire contentsof which is already expressly incorporated by reference, provides a moredetailed description of FIG. 2.

FIG. 3 shows exemplary methods for tag placement of the utility assets,according to some embodiments of the present invention. In someembodiments, the invention creates a multifaceted set ofmethods/standards (QC_STANDARDS) that are applied throughout theQC_PROCESS. QC_STANDARDS apply to data schema and model, process andprocedures, TAG physical configurations and placement on INFRA and TAGread or writes both above and below ground and audit and compliance andpublic and private interface and access to DATA_SET.

The following are few examples of the methods/standards that the presentinvention creates:

-   -   ADMINISTRATIVE—Standards for collecting administrative data        related to INFRA projects.    -   ENGINEERING—Standards relate to provision of engineering        formulas and calculations that are utilized by the system.    -   FIELD INVENTORY—Standards for naming and numbering field        components and units within the context of INFRA projects and        also within the context of linking with upstream manufacturers.    -   RFID INVENTORY—Standards for naming and numbering RFID TAGs        within the context of INFRA projects and uniquely per TAG in        order to tie them to data associated with them.    -   WORK UNIT—Standards for the scope and data requirements        associated with units of work associated with INFRA projects to        ensure compliance and PIM.    -   TAG_LIFE—Standards for the commissioning, placement, geospatial        referencing and linkage to data of RFID tags used in INFRA        projects.    -   DATA_LIFE—Standards for the life cycle development and        collection and audit of data associated with INFRA projects.    -   DATA_SET—Standard data model that is PODS compliant and        generically useable by various geospatial computing        environments.    -   GEOSPATIAL—Standards for the collection of geospatial data in        accordance with accepted methods and best practices and in        particular related to QCIA TAGs.    -   QUERY—Standards for query of RFID data in the field and for        public and private access of related data including national        security requirements and other safety requirements.    -   ENGAGEMENT—Standards for required engagement of inspectors and        their proxies in the field in order to assure proper data        collection, oversight, and audit during the QC_PROCESS.    -   AUDIT—Standards to ensure that sufficient data has been        collected for each unit of work in support of the PIM goal.    -   COMPLIANCE—Standards to ensure that data acquired is supportive        of compliance requirements associated with WORK_UNITS.    -   LAST MILE VALIDATION—Standards related to the placement, color        and type of TAGs that inherently provide validation and        information both visually and via electronic means of what is        being seen on the INFRA.    -   SECURITY—Standards related to data security and compliant with        Industry and national standards as required.

During the application of the QC_PROCESS by the QCIA program, variouspoints and segments of interest are identified for data collection,documentation and audit. Points of interest are called QC_POINTS,segments are called QC_SEGMENTS. Components and units that are used tobuild the pipeline are also tagged with INVENTORY tags. The TAG_LIFEstandard sets forth the configuration of the TAGS, their placement onINFRA and the linkage of the TAG to the appropriate DATA_SET associatedwith that TAG.

The results of the application of the standard TAG_LIFE determinevarious methods of attaching RFID TAGs to sections of pipe. The TAG_LIFEstandard sets parameters for the placement and spacing of TAGS near oraround or upon various components of INFRA.

As shown in FIG. 3, METHOD 1 shows an RFID tag attached to a pipesection with 2 HEAVY DUTY ZIP STRAPS. METHOD 2 shows an RFID tagattached to a pipe section with (1) 1 heavy duty strap per tag and withthe RFID tag wrapped with pipeline tape. Note that the RFID TAG shown inMETHOD 2 is shown placed with the End of tag at end of sleeve or epoxyweld cover.

METHOD 3 shows and RFID TAG placed on a pipe section using a 1 heavyduty zip strap per tag and a 1 pipeline sleeve (assuming proper heatresistance of the chip). Note that the tag is again placed in a standardposition from the weld based on TAG_LIFE standards.

Tags may be of different colors and form factors for placement onvarious types of surfaces. The following is an exemplary list ofdifferent color schemes, according to some embodiments of the presentinvention:

-   -   Yellow Tag: Inventory Tag—formed to pipe diameter. Tag placed on        pipe during stringing operation used below ground 1 to 3 tags        used. Tag is linked to the joint work unit. Also used for        vessels & tanks.    -   Green Tag: Inventory Tag for flanges, fittings. Formed or        flexible and usually used above ground. Tag is linked to the        flange or fitting work unit.    -   Blue Tag: Inventory Tag—For above ground Pipeline units. Used to        Tag surface components attached to the buried pipeline. Tag is        linked to the Pipeline Status work unit.    -   Red Tag: Join Tag; to be used for each joint. Placed on the        upstream side of joint. Tag is linked to the join work unit.    -   Orange Tag: Tie-In Tag; used for each tie-in placed on the        up-stream side of JOIN. Tag is linked to the tie-in work unit    -   Black Tag: Valve Tag; used for each valve & Actuators. Placed on        the valve body. Tag is linked to the valve work unit

The following is an exemplary list of different tag types, according tosome embodiments of the present invention:

-   -   Pipe Joint Seamless pipe. Used for surface piping. Linked to        Inventory Pipe work unit.    -   Heat Zone This zone will be affected by welding heat    -   Flange—For connecting pipe lengths usually on the surface.        Formed or flexible and usually used above ground. Tag is linked        to the flange or flange work unit    -   Fitting Tag is placed in the center of fitting. Formed or        flexible and usually used above ground. Tag is linked to the        flange or fitting work unit    -   Valve (flanged)—Tag is placed on the side of valve flange.        Formed or flexible and usually used above ground. Tag is linked        to the flange work unit    -   Valve (Welded/Threaded)—Tag is placed on the side of valve Body.        Formed or flexible and usually used above ground. Tag is linked        to the valve work unit    -   Nipple (TBE)—Nipple is considered pipe. Tag is linked to the        pipe inventory work unit. Also used for vessels & tanks    -   Weld-O-Let—Fitting Tag is linked to the fitting inventory work        unit. Also used for vessels & tanks    -   Pipeline—Line pipe underground—Shows tag placements    -   Join Area—Join coated with plastic sleeve or epoxy.    -   Surface Pipeline warning sign—All pipelines are required by law        to have signs spaced along the ROW over the line. Tag is linked        to pipeline Status work unit    -   Cathodic test post—All pipelines are required by law to have        Cathodic posts along the ROW over the line. Tag is linked to        pipeline Status work unit

In some embodiments, QC_PROCESS requires a user to interface (QC_ENGAGE)with INFRA activities in order to collect data. The primary method forforcing this engagement, above and beyond the process itself, is theaudit program which, when executed, notifies the inspector ofinformation that must be collected related to QC_POINTS and QC_SEGMENTSwithin the context of WORK_UNIT. If required data is not collected, oris outstanding based on system criteria, the audit function will flagthis shortfall of data and who (inspector or proxy) is responsible forthis non-compliance.

In some embodiments, QC_ENGAGE facilitates the engagement of inspectionresources in an optimized manner. QCIA provides field data collectiondevices and resources that facilitate and supports the various types ofdata collection and interface and presence including data collection,photographs, voice, videos, location (e.g., GPS) points and RFID TAGreads and writes provided in the form of ruggedized and explosion proofcertified field computing devices.

In some embodiments, a QC SEGMENT is an automated process that organizesdata in groupings associated with segments of a pipeline or utilityinstallation that have attributes that point to or indicate possibleanomalies or inspect regimens that are applicable to these regions.

FIG. 4 is an exemplary process flow for the opening and closing of afile or data set of information, according to some embodiment of thepresent invention. The QC_PROCESS incorporates WORK_UNIT, which is thelogical division of work into centers of activity that require audit insupport of PIM. WORK_UNIT is logically connected to QC_POINTS andQC_SEGMENTS. QC_POINTS and QC_SEGMENTS are locations and boundaries thatare tagged and identify areas and points of data collection interestduring the life cycle of INFRA and tagging is controlled by the TAG_LIFEprocess.

In some embodiments, the invention logically divides or groups(NATURAL_GROUP) INFRA projects into WORK_UNIT and applies datacollection and audit criteria to each unit of the WORK_UNITS. In someembodiments, Data and meta-data associated with a WORK_UNIT is collectedjust in time (JIT) as data is completed or available, but notnecessarily in a linear sequence. The invention audits to validate thatall data required for audit or compliance of a WORK_UNIT is complete, inthe field or afterward.

In some embodiments, WORK_UNIT includes OPEN_WORK and CLOSE_WORKautomated processes that systematically define the business rules forthe opening and closing of, in effect, a file or data set of informationon each WORK_UNIT. OPEN_WORK and CLOSE_WORK do not require sequentialprocessing but allow for the fact that data is available at differenttimes during the course of work on INFRA. For example, a RepairWORK_UNIT may be closed and audited days after the repair is coveredover and buried. Audit functions as a QC check to make sure that alldata required to close a WORK_UNIT has been acquired.

In some embodiments, OPEN WORK UNIT and CLOSE WORK_UNIT include thefollowing processes, executed by one or more processors:

-   -   Open WORK_UNIT by the QC_PROCESS system interface.    -   Control the acquisition of data by DATA_LIFE.    -   Set up and collect Prep data for the work that is to be done.    -   Set up Provision of materials and collect as materials for the        job are provisioned and provided in the field.    -   Create Staff manifest which tells system who is doing the work.        Operator qualifications have previously been entered into the        systems.    -   Capture environmental data concerning the conditions under which        the work is being. This includes ambient temperature, soil        conditions etc.    -   Perform work collect and appropriate data regarding the work        accomplished.    -   Test work. Test results are captured on site or are available        afterward.    -   Tag POINTS OR SEGMENTS.    -   Control the standards and methods applied to tagging by TAG_LIFE        process.    -   Run AUDIT program against the WORK_UNIT to test that all data        has been collected.    -   Close WORK_UNIT based on AUDIT results.

OPEN_WORK_UNIT—CLOSE WORK_UNIT are logical sequence of data collectionand the tagging of infra associated with a logical grouping of work. Forexample, the repair of a discrete section of pipe could be a WORK_UNIT.

Block 401 represents the beginning of the WORK_UNIT process. The QCIAsystem allows the project engineer of field manager to define aWORK_UNITS (such as a discrete pipeline prepare as a WORK_UNIT.

Block 402 represents the fact that the QCIA system of the invention isapplying an overarching set of data collection standards which is calledthe DATA_LIFE process to the collection of all data associated with theWORK_UNIT. DATA_LIFE is a business rules based set of standards thatensures that all required data is collected in the context of the needsof the particular type of work being done (the WORK_UNIT) defines theparticular type of work being done and defines the data required tocomplete the audit function.

The invention provides the ability to configure the data needsassociated with the work done in various types of WORK_UNITS. This givesthe operator the ability to customize the business rules associated withvarious types of work being done in the field. Business rules and datarequirements may change between build, repair or maintenance activitiesand the DATA_LIFE standard enforce these rules by requesting data inputsat various stages of the completion of the WORK_UNIT.

In some embodiments, the invention uses a just in time (JIT) datacollection concept. Data is collected when it is appropriate to collectthe data. For example, ambient temperatures needs to be collected at thetime that a JOIN (weld) is being performed. Data in the JIT concept doesNOT have to be collected in any particular sequence or order, but itneed to be collected based on the business rules set that apply to theparticular type of WORK_UNIT being undertaken.

Block 403 represents the collection of all data associated with thepreparation (PREP) of the work to be done in order to complete theWORK_UNIT. Examples of this data are administrative project information,worker qualifications, ownership etc.

Block 404 represents the collection of data associated with theprovisioning (PROVISION) of components and units. For example, as pipesegments, flanges and pipe weights are provisioned out of inventory intothe field in support of the repair, data is collected about each ofthese components and units.

Block 405 represents the collection of staff and worker information(STAFF). As an example, data associated with the field testing ofwelders can be collected at this point.

Block 406 represents the collection of environmental data(ENVIRONMENTAL) associated with both weather and ditch conditions. Forexample, the ambient temperatures that exist during a repair thatinvolves welding, is critical information and the conditions of theditch (wet, dry, frozen) is also critical.

Block 407 represents the performance (PERFORM) of the primary action ofthe WORK_UNIT. For example, if the WORK_UNIT is a pipeline repair, theprimary PERFORM function may be the cutting out of a damaged section ofpipe, the welding in of a new section and the disposition of the damagedsection. Any PERFORM function will require the application of a numberof standard modules that are provided by the system. For example, thepreviously described repair would require the JOIN module, INSPECTmodule and TEST module in order to collect all data associated with therepair and to appropriately TAG the repair.

Block 408 represents the testing and inspection (TEST) of the work thathas been performed in block 407. For example, during a pipeline repairthat involved a JOIN in block 407 there would be pressure testing on thepipe segment as well as NDE X-ray of the JOIN.

Block 409 represents the tagging (TAG) of appropriated sections of theINFRA. For example, if a section of pipe has been cut out and a newsection is joined, the JOIN will have a JOIN TAG placed in a locationnear the JOIN. The placement of the TAG in relationship to the locationof the JOIN, the color of the TAG and the data associated with it arecontrolled by the business and rules provided by the TAG_LIFE process.

Block 410 represents an audit function. The audit function is a businessrules driven process that validates that all required data collectionand tagging functions have been performed based on business rules andparameters set by the administrative set up of the WORK UNIT. The auditfunction performs a query of the existing data base of collected dataand the data associated with validation of proper tagging processes anddelivers a real-time status to the field or the office operator. Forexample, after a pipeline repair has taken place, but before the ditchhas been covered, the audit function can be run to see if any dataassociated with the repair is missing. A WORK_UNIT cannot be closed(from and audit standpoint) unless all data, as set forth in thebusiness rules and all tagging as set forth in the rules has beencompleted.

Block 411 represents the control of tagging controlled in blocks 407-409of the WORK UNIT by the TAG_LIFE standard and process. TAG_LIFE iscrucial to making sure that work that is done on INFRA is properlytagged and that the TAG is properly installed, the GPS data included fand that the TAG is linked to data associated with the TAG. For example,a JOIN TAG may be placed (under the standards of TAG_LIFE) at a certainposition next to the actual joint on the pipe. The installed tag may bea certain color and may include location (e.g., GPS) data. All of theseactivities are controlled by TAG_LIFE. The AUDIT function also queriesTAG_LIFE to validate that the install and linkage of the TAG andassociated data are completed.

Block 412 represents the logical closing of the WORK_UNIT from a datacollection and tagging perspective. For example, if the WORK_UNIT was apipeline repair, all data required to document the repair has beencollected and the repair has been tagged, the tag also includes location(e.g., GPS) data to establish its location. The audit program has beenrun validating the completion of all data collection and tagging tasks.The pipeline repair is fully documented.

In some embodiments, the invention incorporates an automated process,executed by one or more processors, for identifying points of interest(QC_POINTS) and segments (QC_SEGMENTS) of interest on INFRA andcollecting sets of data associated with these points and tying thesepoints and associated data to TAGs both above and below ground.QC_POINTS and QC_SEGMENTS are data model attributes of DATA_SET.

In some embodiments, QC_POINTS includes the following types:

1. Components—INFRA components like pipes, fittings and flanges.

2. Units—INFRA units like weights.

3. Joins—Welds and joins of INFRA.

4. Repairs—Repairs to INFRA

5. TIE-INS—Tie-ins to INFRA

6. Crossings—Third party crossings of INFRA or other utility assets,archeological sites, or other restricted areas, or crossings of roads,rivers etc.

7. Starts Ends—Beginnings and ends of QC_SEGMENT.

In some embodiment, a wide variety of features and areas may bepresented by or attached on a pipeline or other INFRA that qualifyeither as QC_POINTS or QC_SEGMENTS as part of the QC_PROCESS implementedby the QCIA system, according to the present invention.

A QC_POINT represents pipeline cut out/repair, pipeline warning sign,and an underground tie-in (Junction). If the pipe has leaked orruptured, a section (Cut Out) is removed and replaced with new pipe thatmeets or exceeds the specs of the cut out pipe. Warning signs arerequired by code to be spaced at set intervals along the pipeline and atcrossings.

FIG. 5 depicts an exemplary QC_SEGMENT, according to some embodiments ofthe present invention. In some embodiments, the invention derives orcreates a new inspection centric view (IC_VIEW) of INFRA, especially inregard to a pipeline infrastructure. A QC_SEGMENT is a logical segmentof a pipeline that has a beginning and an end and which provides aspecial area of interest for the purpose of test or inspection. Forexample, pressure tests are completed on subsections of pipeline andthese subsections are defined ad hoc from one point of the pipeline toanother based on multiple considerations at the time of the test. Dataabout the test and the actual segment of the INFRA involved in the testis circumscribed and identified by the invention as a QC_SEGMENT and iscalled a TEST_SEGMENT.

QC_POINTS or QC_SEGMENTS are defined by the QCIA system as points orsections that are to be tagged with RFID TAGS. The type of TAG and theplacement of the TAG at each point or at the beginning or end of eachsegment is defined and controlled by the TAG_LIFE process that isconfigured with TAG and tagging related business rules by the system atthe beginning of each job or project. It is noted that inventory itemsare tagged with INVENTORY_TAGS. Pipeline components and units that areprovisioned into the field and installed are tagged as inventory, butare not normally geo-referenced with regard to their location. It ispossible that a pipe segment would have several tags, inventory tagsthat tie in information about the specifications of the pipe andQC_POINT Tags that show key points on the pipeline like JOINS. A sectionof pipe could also have a beginning of QC_SEGMENT or end of QC_SEGMENTtags. Inventory tags are typically not geo-referenced all other tags arenormally geo-referenced.

A QC_POINT may include a Pipeline Riser, The riser brings the subsurface pipe to the surface to tie into a facility. A QC_POINT may alsoinclude a Pipeline Transitions. Usually a 3′ piece of pipe that ismachined at each end to match line pipe and riser. Because surface pipeand line pipe are different in thickness and property make up atransition piece must be welded in.

A QC_POINT may include THRUST/ANCHOR made of concrete or steal.THRUST/ANCHOR are used to hold pipe in high pressure and expansionsituations. A QC_POINT may include PIPE EXPANSION. Due to heating andcooling the pipe expands Line pipe is designed to allow for pipeexpansion due to temperature of the product. A PIPELINE WEIGHTS may alsobe represented by a QC_POINT. Usually made of concrete and bolted on orsaddled on using no bolts, pipe weights are used in none trenched watercrossings, flood plains and muskeg to stop the pipe from floating.

A PIPELINE SAG may also be represented by a QC_POINT. A bend pulled inthe line pipe. A pipe sag is a engineered bend to drop the conform thepipe to the ditch bottom. A QC_POINT may include Pipeline Overbend. Abend pulled in the line pipe. A pipe over bend is a engineered bend todrop the conform the pipe to the ditch bottom

A PIPE JOIN, which is a method of joining pipe in a continuous string apipe join could be welded, mechanical or fused, may also be representedby a QC_POINT. A ROCK SHIELD START may also be represented by aQC_POINT. The start of pipe protection Rock shield is used to protectthe external pipe coating; start include GPS data. A QC_SEGMENT mayinclude a ROCKSHIELD END. The end of pipe protection Rock shield is usedto protect the external pipe coating and includes location (GPS) data.

An INVENTORY TAG represents a line pipe. A joint of pipe that isexternally coated and may be internally coated, in lengths of 20′-40′-or 60′ Line pipe is specifically designed for the product, pressure andenvironment and comes in triple, double and single random lengths.

A QC_SEGMENT represents a CROSSING ENTRY; the up-stream entry point ofwhere the drag section joins the mainline Crossing entry is thebeginning of the crossing bore whole or open cut on the upstream side ofpipeline. A OBJECT CROSSED may also be represented by a QC_POINT. Theobject crossed could be a roadway, railroad, water course, anotherpipeline, or cables

An OBJECT CROSSED may also be represented by a QC_POINT. There can bemultiple items in a single crossing. A QC_SEGMENT may include a CROSSINGEXIT, the down-stream exit point of where the drag section joins themainline. Crossing exit is the beginning of the crossing bore hole oropen cut on the down-stream side of pipeline.

A PIPELINE SIDE BEND may also be represented by a QC_POINT. A SIDE BENDchanges direction of the pipeline. A QC_POINT may also represent aDITCH/DRAINAGE. In mild to severe elevation changes, DITCH blocks areused to keep the ditch soil material in place and safe from erosion. ASURFACE DRAINAGE may also be represented by a QC_POINT. Surface drainageitems are put in place to direct water off the right of way.

A QC_POINT may represent cathodic test post. Test posts are put in placeon the surface so corrosion technicians can take cathodic currentreadings and coating holiday repairs. Coating holidays repaired duringconstruction are weak points in the coating integrity and need to betracked as a point of later inspections. A QC_POINT may also representan in line surface facility. A surface facility is a component, unit,compressor station, pump station, gas plant or any apparatus a pipelineis connected to for separation, storage and or processing the producttransported by the pipeline.

As another example, pipelines may travel through ditches in whichenvironmental conditions of the ditch can change, sometimes, radically.For instance, a ditch may begin in sand and then travel through mud andwater. From an inspection point of view, anomalies of a specific typeover time would be expected based on the change in environmentalconditions within the ditch. The invention defines changes inenvironmental conditions of the INFRA within a QC_SEGMENT which might becalled DITCH_SEGMENT. DATA_SET information regarding the DITCH_SEGMENTcould lead future inspection to specific QC_SEGMENTS and provide for ahighly efficient and cost savings approach to inspecting and testingbased on assumed or expected problems associated with the QC_SEGMENT.

In some embodiments, a QC_SEGMENT may be tagged at the beginning of thesegment and at the end of the segment. Each tag is geo-referenced sothat the segment, and all QC_POINTS and all data associated with thatsegment can be viewed as one grouping of data.

A QC_SEGMENT differs from a pipeline segment in that a QC_SEGMENT isprimarily designated on the basis of changes in the environmentalconditions within the pipeline ditch itself. The segment providesinspectors and engineers with information that will lead them to lookfor particular types of anomalies that arise under the varyingenvironmental conditions described by the QC_SEGMENT.

A pipeline is typically made up of pipe segments welded, or somehowjoint together. There may be a one to one correlation between a pipelinesegment and a QC_SEGMENT, but more often there will be multipleQC_SEGMENTS within the boundary conditions of a traditional pipelinesegment. For example, two pressure test QC_SEGMENTS that overlay maydesignate the starting and end points of two separate pressure teststhat were done on the pipeline, and two traditionally designatedpipeline segments may belong to the same pipeline.

Also, individual QC_REFERENCE POINTS may designate points of interest onthe same section of pipeline. Moreover, a QC_SEGMENTS may designatechange in environmental conditions in the ditch along the length of thepipeline.

A pipeline can have from one to multiple test segments and for manyreasons, for example, a Start Point Pressure Test, which includeslocation (e.g., GPS) data. Typically, the test segments are not tiedtogether until the tests are successful. Each test segment is numberedand GPS's at start & finish of segment. The test info are linked to thetest results.

A pipeline may also have from one to multiple test segments and for manyreasons, for example, End/Start Point Pressure Test, which includes GPSdata. The test segments are not tied together until the tests aresuccessful. Each test segment is numbered and its GPS data is collectedat start and end of the segment. The test info are linked to the segmentnumbers.

End Point Pressure Test, which includes GPS data, represents the end ofpressure test segment and pipeline segments designated as such, may usetraditional definitions of pipeline segments. In some embodiments, apipeline segment starts with the pipeline start point and continuesuntil one of the following happens:

1 The design of the pipe changes,

2 The pipe ties into a facility, valve station or another pipeline,

3 The pipe passes from one class area into another class are, or

4 The pipe passes through a state, provincial or country border.

Tie-In QC_POINT is tied into a riser, expansion loop, underground tee,y-lateral, WOL, etc., and a Join is tagged with links to the tie-ininformation. Repair QC_POINT (which may include GPS data) may be acoating, repair or; a pipe cut out, or a mechanical repair, cut outs andmechanical repairs and is tagged.

Crossing QC_SEGMENT represents the installation of units such as swampweights, thrust or anchor blocks, casing, cathodic posts, epoxycoatings, coatings, rock shield, sand, ditch blocks, expansion loops,insulation etc. The beginning and end points of the segment include GPSdata and are tagged.

Unit Install QC_POINT represents the installation of units such as swampweights, thrust or anchor blocks, casing, cathodic posts, epoxycoatings, coatings, rock shield, sand, ditch blocks, expansion loops,insulation etc. These items includes GPS data when in place. The surfaceunits like casing vents, cathodic posts, risers, and pipeline warningsigns are tagged with pipeline information and include GPS data.

JOIN QC_POINT represents the joining of individual pipe to another pipethat will constitute a segment, by welding, fusion or mechanical means.Each join is tagged with links to the welding information.

QC Segment Identified by the type of ground may be observed whileditching operations are being carried out. The QC section is identifiedby GPS at start and finish. A pipeline could have only one QC segment ormultiple segments. A Crossing Segment (drag section) is tagged andincludes GPS data. TAGS are linked to crossing information. If the dragsection was installed through a bore hole, The soil type may not beidentifiable. There can be multiple items crossed in a single crossing.

In some embodiments, QC Segment is identified by the type of groundobserved while ditching operations are being carried out. The QC sectionmay be identified by GPS at start and finish.

FIG. 6 is a representation of various types of QC_SEGMENTS that may bedefined in a normal pipeline scenario, according to some embodiments ofthe present invention. Note that QC_SEGMENTS may be subset of normallydefined (industry standard) pipeline segments. For example:

in a QC-SEGMENT 1, Ditch conditions are Sandy Loam,

in a QC-SEGMENT 2, Ditch conditions are Gravel,

in a QC-SEGMENT 3, Ditch conditions are Clay,

in a QC-SEGMENT 4, Ditch conditions are Muskeg,

in a QC-SEGMENT, Ditch conditions are Sandy Clay,

in a QC-SEGMENT 6, Ditch conditions are Clay and Rock,

in a QC-SEGMENT 7, Sandy Loam,

in a QC-SEGMENT 8, Ditch conditions are Clay and Rock, and

in a QC-SEGMENT 9, Ditch conditions are Sandy Clay.

In some embodiments, the QC_PROCESS includes an automated process,executed by one or more processors, for tying the INFRA to relatedDATA_SET data via TAGs. This process, called OPEN_TAG-CLOSE_TAG.OPEN_TAG-CLOSE_TAG, ties specific data associated with points andsegments of the INFRA to proximately placed TAGs which are attached onor near QC_POINTS and QC_SEGMENT beginning and end points. TAGs frominitial project provision through attachment to INFRA whilesimultaneously allowing for appropriate collection of DATA_SETinformation associated with each type of TAG. This method results in anew level of field validation and repair validation. The methods andrules and types of TAGs that are required by TAG_LIFE may provide afinal validation of build, test, or repair.

For instance, when pipeline repairs are finished there is currently noprocess and method that leaves a TAG on or about the repair area that(a) proves or validates that there was work done on the INFRA and (b)can be queried by a public process that yields appropriate levels ofinformation beyond that which is available on the TAG. Years later whena section of INFRA is uncovered (daylighted, in the case of a pipeline),the TAG left during the build, test or repair can be queried in thefield and tied to DATA_SET data that was collected earlier during theactive life cycle of managing the INFRA. TAG_LIFE also provides for atagging standard (TAG_TYPE) that requires that TAGs of different colorand design be placed in specific location (for example, upstream ordownstream) of facilities features resulting in a standard method forinterpreting visually or through electronic means, what the TAGrepresents. The unique combination of process (TAG_LIFE) and taggingstandards (TAG_TYPE) provide a new environment for LAST_MILE validationof INFRA.

FIG. 7 shows a read/write process of locating RFID tags that have beenplaced on INFRA according to some embodiments of the present invention.The POINT_STICK RFID read/write capability represents an advancecapability of RFID readers that not only read RFID signals in atraditional way, but also have the ability to discriminate and designatea particular tag from multiple tags that are exposed in the field. Insome embodiments, this is done by a combination of RFID reader and lasertechnology.

A hand-held device 701 (including a processor, memory, I/O components, adisplay, and related software) can identify a particular tag, read itsunique tag identifier and link the DAT_SET associated with that tag whenpointed (702) at an exposed RFID TAG (which is one among many exposedTAGS is a ditch). This capability gives an inspector, who is observing a(uncovered or exposed) section of ditch the ability to stand at the edgeof the ditch, to visually see a tag, to aim the POINT_STICK device at aselected TAG and to acquire data about the tag. The worker using thehand held POINT_STICK IFR or laser GPS device may point to a TAGposition and read unique TAG Identifiers and link geo-reference positionof tag with appropriate DATA_SET that was created when TAG was placed.For example, a particular type of TAG that has been placed 703 might bean INVENTORY TAG that is associated with a DATA_SET that hasspecifications of the pipe. Another particular type of TAG that has beenplaced 704 might be a JOIN TAG that is associated with a DATA_SET thathas data about the join operation.

In some embodiments, an exemplary QCIA process results in multiple typesof TAGs being placed for a pipe prior to its being loaded into the ditchincluding the following tags:

-   -   Join TAG—Join Tag—Tag is Red—placed at every join and        corresponds to Join Work Data;    -   JOIN c/w Sleeve protecting weld plastic sleeve or epoxy coating        covers the JOIN area;    -   PIPE JOINT—Line pipe;    -   PIPE SUPPORT—Supports are usually wooden, plastic cones, or air        bags or sand bags;    -   INVENTORY TAG—Tag is Yellow;    -   INVENTORY TAG (in alternate Position)—All pipe, fittings,        flanges & Pipeline units are tagged and include GPS data;    -   Top of excavated ditch;    -   Ditch Wall; and    -   Ditch Bottom.

In some embodiments, an exemplary process for placing a TAG includes:

-   -   All Tags are placed on the pipe prior to the pipe being buried.    -   The pipe is lowered into the ditch and a final jeeping test is        performed looking for surface anomalies.    -   The worker walks the pipe as it is being lowered into the ditch        and using the POINT_STICK device, geo-references each TAG by        pointing at the TAG with a laser range finder capability,        validating the TAG number and linking the geo-reference        information to the TAG and thus the Data SET.    -   At the end of this process, all TAGS are placed on the pipe, the        pipe is lowered into the ditch and all tags are geo-referenced        into their actual position on the earth.    -   Later, when the pipe is uncovered for any reason, the same        device can be used to point at a particular tag and bring up        related data to it.

In some embodiments, the invention is further capable of providing (a) adesign (BANG_STICK) for an optimized below ground reader and (b) adesign for attaching a gas sensor to a buried RFID chip and (3) a design(POINT_STICK) for identifying and reading and writing to specific tagsas they are lowered into the ground despite the fact that multiple tagsare broadcasting simultaneously. For example, as a pipeline is beinglowered into the ditch and is passing through its final ‘jeeping’ test,QC_PROCESS provides the capability to identify the TAG uniquely and toGPS its location via a combination of GPS and laser technology as it isbeing lowered into the ground. In some embodiments, the QC_PROCESSadditionally provides for the ability to single out one TAG among manythat have been Daylighted and to query that individual TAG from adistance.

FIG. 8 is an exemplary process for reading RFID tags that are buriedunderground according to some embodiments of the present invention. Insome embodiments, below ground reads are accomplished by a ‘bang stick’RFID reader (BANG_STICK). The BANG_STICK reader utilizes an enhancedsignal that is aimed and focused into the ground only when the readerantennae are directed into the ground. The enhanced signal is approvedbased on the unique feature that the BANG_STICK can only be used forreading sub-surface TAGs. TAGs of either passive or active design can bequeried at depths below ground that allow them to be used on allcommercial INFRA internationally.

TAGs that are read are linked back to publicly accessible sites toprovide initial information on the INFRA on or about which the TAG isplaced. A PUBLIC_READ software can be used on a wide variety of handheld devices such as mobile phones or tablets. PUBLIC_ACCESS providesvirtually anyone the ability to read a TAG, which is Daylighted, usingan electronic device such as a computer, PDA, mobile phone, and the likeHowever, access to DATA_SET is strictly controlled beyond basic safety,ownership and identification that is provided to the general public.

Referring back to FIG. 8, a bang_stick 801 is held against the groundand rotated to search in a circular pattern for RFID signal. Thebang_stick is GPS enabled allowing it to find location directly aboveRFID chip that has been previously geospatially located (X,Y,Z) duringthe TAG_LIFE process. Antennae 803 provide a powerful and focused beamof energy into the ground. The signal 804 is focused and can be modifiedin strength and coverage by the operator. TAGs 805 of specialmanufacture and design can last for many years below the ground and areoptimized to be read at depths from the surface. A worker searching fora given RFID chip or chips finds the approximate location of buried TAGSusing GPS coordinates from the QCIA system that were developed duringthe TAG_LIFE process when INFRA was tagged and the tags weregeo-referenced.

As shown in FIG. 8, the operator placing an antennae array flat on theground in a location indicated by previous GPS data. The worker sends afocused and strong signal into the ground, by the bang_stick 801, tosearch for the tag by sweeping the direction of the antennae 803 in acircular motion, thus allowing for a radius search for the tag in thecandidate search area.

RFID chips 805 of both active and passive design, which have an extendedlife are capable of operating underground under the harshest ofenvironmental conditions, emit a response that is specifically designedto be read and optimized by the advanced search capability previouslydescribed.

In some embodiments, the bang_stick reader 801 may be used to readoutput from the buried tag 805. The buried tag may have sensor attachedto it for gas molecules leaks. The tag sensor (TAG_SENSOR) may be activeor passive. In some embodiments, one or more bits of data is used toindicate a gas molecule leak. The active or passive sensor designed tosense presence of natural gas molecules.

In some embodiments, DATA_LIFE is a computer executed process thatcombines business rules and QC_STANDARDS for collecting data at keytouch points to fully populate the data model of the DATA_SET. DATA_LIFEutilizes QC_ENGAGE, TAG_LIFE, WORK_UNIT, and audit functions and is thecheck and balance to field audit practices and derives audit and qualitydata assurance. For example, DATA_LIFE controls the list of dataelements that must be populated for each WORK_UNIT and each TAG to passany audit. The Audit program, using the business rules of DATA_LIFE,queries DATA_SET to verify that all data elements are populated in orderto close out at WORK_UNIT or TAG.

TAG_LIFE is a computer implemented process for provisioning, commission,reading and linking TAGs to infrastructure and to collected data duringthe QCIA life cycle. The following is an exemplary process for TAG_LIFE.

-   -   Project is set up and all administrative data is input;    -   RFID TAGs are inventoried and unique project numbers assigned to        tags. A list of the assigned Projects/Tags in stored in a table        or database;    -   TAGs are commissioned onto jobs as needed;    -   OPEN_TAG is implemented when inspector/proxy is engaged with at        WORK_UNIT task that will be tagged at the end of the task;    -   TAG is read by RFID reader which sets the TAG unique identifier        as a key field for the data that will be collected around it;    -   TAG type is declared based on type of task being performed;    -   Data is collected;    -   Data collection is controlled and prompted by DATA_LIFE business        rules;    -   TAG is installed and placed on QC_POINT or beginning or end of        QC_SEGMENT based on TAG_LIFE rules;    -   Position of tag is geospatially referenced;    -   TAG is queried to test that all data is correct;    -   TAG is CLOSED indicating that the OPEN_TAG-CLOSE TAG process has        been completed;    -   DATA_LIFE process links TAG data to QCIA system level reporting;        and    -   AUDIT is run to verify close loop of DATA_LIFE.

FIG. 9 depicts an exemplary process flow for opening tags and closingtags (OPEN_TAG-CLOSE_TAG), according to some embodiments of the presentinvention. OPEN_TAG-CLOSE_TAG is a computer implemented process foropening and closing TAGs that controls the linkage between datacollection, the proper type of tag, the tagging of INFRA and thegeospatial locating on the tag.

In block 901, a user (e.g., an Inspector) logs into the system andidentifies that he/she is prepared to collect data and to place RFIDtags associated with work that is being done on a pipeline or otherINFRA. In block 902, a TAG is opened to begin the process of tagging.OPEN TAG is a command in the QCIA system which provides a set of menusthat controls the type of data that is to be collected for a particulartask. The business rules that control the type of data and the type oftag to be used in the context of a particular task are pre-configuredwithin the QCIA system of the present invention. The TAG is read in thefield to validate the TAG_ID which uniquely identifies the TAG withinthe context of the INFRA project as well as the tie to data that will becollected, in block 903. The inspector or QCIA system user checks out aparticular type of RFID tag from an inventory of TAGS.

For example, if the inspector is going to collect data associated withand intends to tag a JOIN, he/she would remove a JOIN tag. The JOIN taghas a particular shape or form factor required for attachment to thepipe, and is a particular color. Type of tag and color of tag arepre-determined and pre-configured by the QCIA system. The inspector thenreads the unique RFID tag identifier from the tag using a field basedRFID reader. The inspector then tells the QCIA system to attach all datathat is collected and associated with the JOIN to the unique identifierof the tag. The QCIA system also ‘checks out’ the RFID tag from a mastertag inventory, thus providing an accounting for all RFID tags that areused in the field.

In block 904, a TAG type is declared based on the need for a particulartype of tag (DECLARE TAG TYPE). The inspector declares and validatesthat the TAG which has been removed from inventory is of a particulartype or TAG TYPE. In the case of data being collected regarding a joint,the tag type is declared as a join tag. The declaration of the tag typeis the program indicator to follow a set of business rules regarding thecollection of data about the join as well as specifications regardingthe placement of the tag on the pipe near the join.

In block 905, data is collected about the tasks within the WORK_UNIT andlinked to TAG_ID data by the system (CREATE AND LINK DATA). Data iscollected in the field as required based on the activities taking placein the field. The system provides guidance as to what data must becollected. Data collection is not a serial process, since work in thefield is not a serial process. For example, data may be collected for ajob that ends at 5 PM, and the rest of the data collected the next dayor week. Data linked to the unique tag identifier by the system.

In block 906, TAG is placed or installed at the appropriate time duringthe work process. Placement is determined by QC_STANDARD for placement(INSTALL-PLACE TAG). At an appropriate time in the actual work flow inthe field, the RFID tag is placed or installed on or near the QC_POINTor QC_SEGMENT begin or end as relevant to the data being collected forthe particular task.

In block 907, TAG is geospatially referenced to show the position of thetag (GPS TAG). If the TAG represents a QC_POINT or the beginning or endof a QC_SEGMENT, it will be geo-referenced either in place, or once thepipe (with the tag on it) is placed in its final resting place in theditch. GPS data of TAGs ties together the location of QC_REFERENCEPOINTS with all data associated with the TAG. Inventory tags are notnormally geo-referenced.

In block 908, TAG is closed when all data is collected as required bythe TAG_LIFE and DATA_LIFE processes (CLOSE TAG). The inspectorcompletes the data collection and tagging job associated with tasks orjobs in the field by closing the tag (CLOSE TAG). CLOSE TAG is a logicalclosing of the data collection and tagging process but does NOTnecessarily indicate that all data required has been collected. Audit ofthe data collected, and validation of the tagging is a function of theinternal QCIA audit process which, on command, can run a query to checkto see that all required data (per business rules) and all taginstallation rules (per business rules) have been followed. Under idealconditions CLOSE TAG will pass audit.

In block 909, an audit program is executed to assess TAG data withincontext of WORK_UNIT data (INSPECTION AUDIT). Audit function is providedas a function of the QCIA program. At any time during theOPEN_TAG-CLOSE_TAG life cycle the audit program can be run to provide alisting of outstanding tasks or data that is missing from the particularOPEN_TAG-CLOSE_TAG life cycle. For example, if NDE inspection data hasnot been uploaded to the system and attached to field JOIN data, theaudit program will flag this deficiency.

In block 910, an INVENTORY TAG may be created and placed. This type ofTAG is primarily a material and inventory TAG. The system tracks allcomponents and units that are utilized in building INFRA. Inventory tagsare placed on components, units and other features of INFRA. Dataassociated with inventory tags is primarily concerned withspecifications. For example, the heat number and manufacturer and sizeof a pipe would be associated with an inventory tag. inventory tags donot generally include GPS data. Specifications of materials used incomponents and units, other data associated with specification data,like procurement, vendor information etc., may be included with theINVENTORY TAG. Also, specific data about pipeline components like pipe,flanges, valves, weights, rock shield or sandbags may also be includedwith the INVENTORY TAG.

In block 911, a JOIN TAG may be created and placed. This TAG would beattached on or near a JOIN. DATA_SET generated by collection of allassociated data may be linked to the JOIN. Other data associated withJOIN may include photographs, voice recordings, videos, non-engineeringdata like personal comments and observations, data on individuals whoperformed the welding operation, specific engineering data about theweld itself, type of weld etc., specific data about participating welderqualifications and welder field testing and qualification, and actualNDE XRAY or other NDE test results from JOIN/WELD inspection. Note thatthis data is not collected in the field, but is uploaded and linked intothe system when it is provided by the test contractor.

In block 912, a TEST TAG may be created and placed. This TAG would beattached to validate TEST data. The TEST TAG indicates a TEST completedon the INFRA. TEST PEDIGREE DATA is a DATA_SET associated with TESTwhich includes appropriate TEST results as set forth by business rulesassociated with particular type of test. TEST META is another data setthat is associated with TEST and includes photographs, voice recordings,videos associated with TEST may also include non-engineering data likepersonal comments and observations. TEST CONDITIONS is data associatedwith environmental and other ground or ambient conditions surroundingthe TEST. TEST RESULTS are engineering data with TEST results asrequired by business rules. TESTERS is information regarding individualsor contractors performing the TEST. TEST PARAMETERS are parameters orengineering requirements that were applied during the TEST.

In block 913, a REPAIR TAG may be created and placed. This TAG would beattached on or near a REPAIR. REPAIR may include on or more of thefollowing associated TAGs/data:

-   -   REPAIR PEDIGREE—DATA_SET associated with REPAIR which includes        appropriate REPAIR data and results as set forth by business        rules associated with particular type of test.    -   REPAIR DESCRIPTION—data associated with rationale and need for        repair, and approach taken and justification.    -   REPAIR META is other data associated with REPAIR, includes        photographs, voice recordings, videos associated with REPAIR may        also include non-engineering data like personal comments and        observations.    -   JOIN DATA is JOIN data associated if JOIN was required as part        of REPAIR. Most REPAIR work requires some type of JOIN.    -   TEST RESULTS—engineering data with TEST results as required by        business rules. Usually pressure tests associated with repairs        utilizing JOINS.

In block 914, a TIE IN TAG that indicates a place where other sectionsof PIPE are tied in to the main pipeline may be created and placed. ThisTAG would be attached on or near a TIE-IN. The TIE IN TAG may include onor more of the following associated TAGs/data:

-   -   TIE IN PEDIGREE—DATA_SET of all appropriate data required to        document and audit a pipeline TIE_IN.    -   COMPONENTS. Documentation of pipeline components that were used        or involved in the TIE-IN    -   JOIN DATA is JOIN data associated with JOIN that is required as        part of TIE-IN. Most TIE-INS require some type of JOIN.    -   TIE IN META is other data associated with TIE-IN, includes        photographs, voice recordings, videos associated with TIE-IN may        also include non-engineering data like personal comments and        observations.    -   TEST RESULTS—engineering data TEST results as required by        business rules. Usually pressure tests associated with actions        requiring JOINS.

In block 915, a QC_SEGMENT TAG may be created and placed. A TAG thatshows the beginning and end point of a QC_SEGMENT. This type of tagwould designate the beginning or end of a QC_SEGMENT and tie to datadefining the segment. There may be various types of segments thatqualify as a QC_SEGMENT. The QC SEGMENT TAG may include one or more ofthe following associated TAGs/data:

-   -   QC SEGMENT—DATA_SET that fully describes the QC_SEGMENT based on        business rules that define data that is needed to describe each        type of segment.    -   TEST SEGMENT DATA—DATA_SET that would be created if the        QC_SEGMENT represents a segment of pipeline that was tested in a        particular manner.    -   REPAIR SEGMENT DATA—DATA_SET that describes the area in which a        repair of the pipeline was accomplished.    -   QC_SEGMENT DATA—DATA_SET that describes a section of ditch in        which the environmental conditions are consistent, but which are        different from other QC_SEGMENTS of the pipeline.    -   CROSSING SEGMENT DATA—DATA_SET that includes required data to        describe and document CROSSING per business rules of the system.

FIG. 10 shows an exemplary DATA_SET record, according to someembodiments of the present invention. A DATA_SET is defined as a datamodel that incorporates all data elements necessary to link data andinfrastructure locations. The DATA_SET is uniquely created by acombination of its underlying data model combined with interactivemethods of data collection provided by the invention under the guidanceof the QC_PROCESS. The DATA_SET comprises of applicable data associatedwith new pipeline construction, the inspection of the build and thetesting of the build. The invention also provides equivalentdocumentation of repairs to existing pipelines and other relatedstructures. The DATASET is an information model that captures andorganizes the full life cycle data that is required for thedocumentation, testing validation and build characteristics of the newpipeline construction phase within the oil and gas pipeline industry.

In some embodiments, the DATA_SET has the following systemiccharacteristics: (a) PODS, industry data standard compliant andnormalized, and (b) designed for and maintained as Geospatial database.The DATA_SET includes joint creation pedigree and other data that can beused to identify, define, and assure compliance of pipelineconfigurations. Data is stored in a secure manner and is securelyaccessible.

Furthermore, a DATA_SET may:

-   -   a. Allow for creation, at the software application level, of a        comprehensive build ‘pedigree’ for ALL key reference points or        QC-RP in the life cycle of the pipeline build.    -   b. Provide INSPECT data that allows the application layer to        create an inspect audit trail view of the data    -   c. Provide for test data that can be compared to engineering        specs and other standards and also supports and audit of test        performance on the build.    -   d. Be linked relationally, linked to geospatial coordinates and        to RF-UID unique identifiers and to RFID asset management        inventory control identifiers (RFID-DB).    -   e. Be uniquely complete, organized and normalized, and provides        the application layer of the system with the capability to        generate views of data including build, inspect, test views.

Referring back to FIG. 10, block 1001 represents the business rulesprovided by the DATA_LIFE standard which controls the collection andvalidation of data within the QCIA system as the system facilitates theQC_PROCESS. DATA_LIFE is a comprehensive set of business rules thatcontrols and manages the types of data that are required to be collectedand validated during each phase of the QC_PROCESS. In addition tobusiness rules, DATA_LIFE inherently provides rules for data types,field sizes and all other characteristics that are required by standarddatabase architecture. DATA_LIFE is a configurable set of rules thatprovides the QCIA program with the flexibility of supporting varioustypes of data collection projects that may have different datarequirements. It serves as a control function for all data collectionwithin the system.

Block 1001.1 represents all PROJECT/ADMIN data that is collected,primarily by the ADMIN module. This data is administrative in nature andrefers to project codes and ownership. All of this data is available forreference for to extend data that is being collected in the field fromoperational modules. This data is normally collected or imported priorto the start of projects.

Block 1001.2 represents all engineering data, formulas andspecifications that is used by the program to perform requiredcalculations during the operational phases of the program. This data isnormally provided by the project engineer and serves as a basis for allengineering calculations.

Block 1001.3 represents a traditional inventory functionality forcomponents and units. All components and units will be checked intoinventory and then checked out as they are provisioned into the field.Data about the specifications of components and units is entered intothe inventory system as is used and linked to INVENTORY TAGS that areplaced during the TAG_LIFE process support of the completion of aWORK_UNIT.

Block 1001.3 represents an inventory of RFID TAGS which will be providedby various TAG manufacturers. RFID tags are checked out of inventory andare provisioned into the field for use by the QCIA program as needed.This process provides a check and balance to make sure that all TAGSused in the field are accounted for by the tag inventory system.

Block 1002 represents the concept that the WORK_UNIT is a logical‘wrapper’ for all data which is collected and all RFID tags that areplaced associated with logical groupings of work. For example, anindividual or group of pipeline repairs could be considered a WORK_UNITor logical grouping of tasks.

Block 1003 represents the AUDIT function that is applicable to all dataand tags that are associated with a WORK_UNIT of tasks. The AUDITfunction provides users of the QCIA system with the ability to query orAUDIT the status of data collection and tagging. The AUDIT functionanswers the question “Has all data been collected and have all tags beenproperly placed and geo-referenced in compliance with the business rulesset forth by the DATA_LIFE process?

Block 1004 TAG_LIFE represents the specific set of business rulesassociated with linking data that is collected with RFID tags in thefield. TAG_LIFE controls the interface between data collected and theinstallation of TAGS in the field, thus ensuring that TAGS that areplaced on INFRA are tied to data that has been collected. For example, aJOIN will be tagged with a JOIN tag. TAG_LIFE provides the process,business rules, standards, and specifications necessary to ensure that aproper tag type is placed in a proper position on the pipe and that dataassociated with the tag (JOIN data) is linked to the TAG. When the TAGis read, the QCIA program has the ability to recall add data associatedwith that TAG. In addition TAB_LIFE ensures that the TAG is properlygeo-referenced. The AUDIT function looks at data and flags that havebeen set under the control of TAG_LIFE and DATA_LIFE to verify that alldata is in order to pass AUDIT.

Blocks 1004.1 to 1004.6 represents examples of discrete data that iscollected during a QCIA project. This grouping is representative and notcomplete.

Block 1004.1 ENVIRONMENTAL—data associated with environmental conditionsin and around the pipeline or INFRA at the time work is done. Forexample, ambient air temperature at the time a weld (JOIN) is beingdone.

Block 1004.2 ACTORS—Information about employees or contractors andrelevant individuals that are doing work on INFRA. Would includequalifications and field testing data that is relevant to work beingdone.

Block 1004.3 TASKS—Data about the how and what and when of fieldactivities. For example the DATA_SET that is generated when all datathat is required to document a JOIN is collected.

Block 1004.4 TEST and/or INSPECTION—Test or inspection results. Thiscould be pressure tests results or NDE XRAY results.

Block 1004.5 TAG/PLACE—Data associated with placement of a TAG near workor a segment that is to be designated. For example, this includes theunique TAG identifier, possibly another TAG inventory identifier, anddata about form factor, actual placement, and color.

Block 1004.6 GEOREFERENCE—Data from geo-reference of TAG. This includesGPS strings generated as tag is geo-referenced.

FIG. 11 depicts an exemplary system level architecture, according tosome embodiments of the present invention. The architecture(QC_ARCHITECTURE) is unique in its combination of multi-functional fielddata collection software and hardware, RFID hardware and software andGeospatial databases. Field data collection software and hardware stackprovide data collection, RFID read/write, RFID management middleware,GPS, and multi-media, in a single integrated field ruggedized andexplosion proof configuration.

Block 1101 represents the software stack (levels of functionality thatwould reside on a multi-functional field hardware device) that would beused in the field for data collection, tagging and geo-referencing oftags.

Block 1101.a—COMM LAYER—software layer (like WIFI or 3/4G), executed onone or more processors, allows the device to connect to the server orCLOUD.

Block 1101.b FIELD USER INTFC—QCIA program, executed on one or moreprocessors, which controls the data collection and audit functions inthe field. The primary user interface and main USER program.

Block 1101.c—GPS—GPS capability that allows for geo-referencing of TAGSin the field.

Block 1101.d—DATA MANAGEMENT—Data management layer, executed on one ormore processors, controls data being collected from various inputs likeGPS, QCIA program data inputs and RFID reads. This layer integrates datafrom all inputs into a DATA_SET that is then linked with GeospatialDatabase.

Block 1101.e—MULTIMEDIA software—Photo, voice and video capabilitiesthat can link multi-media objects to the QCIA database via the DATAMANAGEMENT layer. Primarily used for the development of META dataassociated with tasks.

Block 1101.f—OS—Operating system layer of the field device—Like MSWindows Mobile.

Block 1101.g—RFID INTFC—RFID read write interface layer to the DATAMANAGEMENT LAYER—this is a software abstraction layer, executed on oneor more processors, which will allow a wide variety of RFID readers tointerface with and share data with the QCIA program via the DATAMANAGEMENT layer.

Block 1101.8—RFID READ/WRITE—RFID read write device/antennae andfirmware that is either integrated into the field device or is connectedto the device.

Block 1102—CHIP MANUFACTURE—OEM (Original equipment manufacturer) ofRFID chips. Chips can be active or passive in design. QCIA system willbe flexible in its ability to use a wide variety of custom or genericchips. The CHIP MANUFACTURE will provide an inventory of chips (Block 3)and also provide an on-line (Block 4) RFID ASSET MANAGEMENT trackingcapability that provides tracking of chips provided to QCIA system useror system provider.

Block 1103—RFID CHIP— RFID chips is provided and serves the purpose oftagging within the QCIA system. In most cases, the chips reside oncustom designed form factors and be created in different colors to beused as part of the TAG_LIFE process. For instance, a JOIN TAG would beform fitted to installation on a pipe and might be colored red.

Block 1104—RFID ASSET MANAGEMENT—Asset management software, executed onone or more processors, provided by the RFID chip manufacturer to keeptrack of chip inventory. As a chip is provisioned into the field fortagging, it is ‘checked out’ of the asset management inventory. Thisserves as a double check and validation that chips checked out ofinventory are, in fact, installed in the field.

Block 1105—RFID MIDDLEWARE—Actively controls the RFID field managementenvironment which is integrated back to the system via the RFIDmiddleware provided by the chip manufacturer that provides extendedfunctionality including field read/write management and other advancedcapabilities. RFID middleware directly supports field read writefunctionality and is optimized for the type of reader/antennae in useand with the types of chips being used in the field. Block 1105 is alsointegrated with block 4 RFID Block 1104 Asset Management layer on thefield device.

Block 1106—PUBLIC RFID READER—OPEN SOURCE or publicallyavailable/commercially used RFID readers. QCIA system provides that thegeneral public will have the ability to read applicable QCIA system RFIDtags. The public reader will direct the public to the block 1108 PublicAccess landing page, where they will find a level of informationconcerning the TAG that will provide contact and public safety orientedinformation. For example, if a person on a walk smells leaking gas, theycan use their mobile phone and a generic RFID reader to access thepipeline data belonging to XYZ corp and they will be given an emergencynumber to call.

Block 1107—GEOSPATIAL DB—The core system of QCIA is a sophisticatedgeo-spatial database and application environment that manages the QCIAapplication program layers as well as maintaining a sophisticatedgeo-spatial enabled database of all QCIA data. An example of this typeof environment is ESRI.

Block 1108—PUBLIC ACCESS—Public access landing page target for allpublically read RFID tags. An individual scans a tag with public orgenerically available RFID reader software and are automatically takento the PUBIC ACCESS LANDING page.

Block 1109—SECURITY INTERFACE—The security interface either stopsfurther inquiry or allows deeper penetration into the system based onpassword and other identification security measures. The SECURITYINTERFACE is directly accessible to those with the proper URL and alsoserves as a back-end to Block 1108 PUBLIC ACCESS. The security accessallows users to access the heart of the QCIA system which resides and isserved up from Block 7 the GEOSPATIAL DB.

Block 1110—ONLINE USER INTERFACE—This is the interface between field andoffice devices and the primary computing facilities and database thatreside on block 1107. When a field inspector is collecting data andtransferring it to the CLOUD it is through the ONLINE USER INTERFACE.Security for this interface is high and requires validation that thedevice that is connected is a safe device and that proper credentialshave been presented.

Block 1111—FACILITY OWNER GEOSPACIAL—Most facility owners maintaingeospatial databases of their facilities at various levels ofsophistication. The system also has the ability to maintain a completegeospatial database or to provide a data set extension to the facilityowner database. For example, if the facility owner maintains their ownsophisticated database and do not want to share it, the system of thepresent invention has the ability to provide an extension data set thatoverlays and enhances the facility owner database with the data that hasbeen developed during the QC_PROCESS. This provides a complete value addto the facility owner without the need for them to release any of theirdata outside of their security areas.

FIG. 12 is an exemplary process flow executed by one or more processors,according to some embodiments of the present invention. The executedmethod performs capturing, organizing and retrieving data for utilityassets using RFID tags, among others. As shown in block 1201, datarelated to a plurality of utility assets in stored in a database,accessible by a plurality of processors. The stored data may includedata about type of the utility asset; repair, documentation, testingvalidation, and inspection of the utility asset. In block 1202, aplurality of RFID tags are programmed for placement on a utility asset.The programming process may include retrieving a unique RFID tagidentifier from the RFID tag using an RFID reader device, linking dataassociated with the utility asset to the unique RFID tag identifier, andchecking out the programmed RFID tag from an RFID inventory database.This enables an accounting for all RFID tags that are used in the field.

In block 1203, the programmed RFID tags are placed on the utility asset.In some embodiments, at least one of the programmed RFID tags is placedon a specific segment of the utility asset as a segment tag, and atleast one of the programmed RFID tags is placed near a specific joint ofthe utility asset as a join tag. In block 1204, the stored data relatedto the utility asset (in the database) is linked with the programmeddata for the placed RFID tags. The linked data includes location data ofthe placed RFID tags.

In block 1205, one or more of the placed RFID tags are queried toretrieve data about the utility asset including data about the locationof the utility asset, the type of the utility asset; repair,documentation, testing validation, and inspection of the utility asset.

It will be recognized by those skilled in the art that variousmodifications may be made to the illustrated and other embodiments ofthe invention described above, without departing from the broadinventive step thereof. It will be understood therefore that theinvention is not limited to the particular embodiments or arrangementsdisclosed, but is rather intended to cover any changes, adaptations ormodifications which are within the scope and spirit of the invention asdefined by the appended claims.

What is claimed is:
 1. A computer implemented method for capturing,organizing and retrieving data for utility assets using RFID tags, themethod comprising: storing data related to a plurality of utility assetsin a database, wherein the stored data includes data about type of theutility assets, repair, documentation, testing validation, andinspection of the utility assets; programming a plurality of RFID tagsfor placement on a utility asset by loading programming data into theplurality of RFID tags, by one or more processors; placing theprogrammed RFID tags on the utility asset, wherein at least one of theprogrammed RFID tags is placed on a specific segment of the utilityasset as a segment tag, and at least one of the programmed RFID tags isplaced near a specific joint of the utility asset as a join tag; linkingstored data related to the utility asset with the programmed data forthe placed RFID tags, including location data of the placed RFID tags;and querying one or more of the placed RFID tags to retrieve data aboutthe utility asset including data about the location of the utilityasset, the specific segment and the specific joint, the type of theutility asset; repair, documentation, testing validation, and inspectionof the utility asset, by one or more processors, wherein said segmenttag includes stored data describing environmental conditions includingsoil conditions of a location where the specific segment was installed,an X-ray of an operation performed on a join of the specific segment,and data describing the environmental conditions including ambienttemperature at a time when a repair was performed on the specificsegment, and wherein querying one or more of the placed RFID tags toretrieve data further comprises executing an audit program to validatethe data or compliance of the data to certain standards.
 2. The methodof claim 1, further comprising generating a report about the utilityasset, according to a plurality of stored rules.
 3. The method of claim1, wherein said stored data related to the plurality of utility assetsincludes one or more of data collection dates and methods, photographs,voice, videos, and location points, related to the utility asset.
 4. Themethod of claim 1, wherein said programming RFID tags include retrievinga unique RFID tag identifier from the RFID tag using an RFID readerdevice; linking data associated with the utility asset to the uniqueRFID tag identifier; and checking out the programmed RFID tag from anRFID inventory database.
 5. The method of claim 1, wherein said join tagincludes data about the specific joint of the utility asset includingdata about the person who performed any repair or operation on thespecific joint, the date of the repair or operation and the type of therepair or operation.
 6. The method of claim 1, wherein said segment tagincludes one or more of the following: associated data describing thespecific segment; data related to testing or validation of the specificsegment; and data describing the area in which a repair of the segmentwas performed, according to a plurality of stored business rules.
 7. Themethod of claim 1, wherein said segment tag further includes stored datadescribing a location of any crossing of other utility assets with thespecific segment data including data about one or more of restrictedareas, roads, and rivers.
 8. The method of claim 1, further comprisingprogramming a repair RFID tag and placing the programmed repair RFID tagon or about a repair area on the utility asset to describe and validatea repair work performed on the repair area.
 9. The method of claim 1,wherein said audit program validates that all required data and all taginstallation rules have been followed, according to a plurality ofstored business rules.
 10. The method of claim 1, further comprisingpointing an RFID reader device to the utility asset including the placedRFID tags; distinguishing and identifying a particular placed RFID tagfrom the placed RFID tags by the reader device; and retrieving data fromthe identified RFID tag by the reader device.
 11. The method of claim10, further comprising generating a plurality of revised data recordsfor the utility asset based on the retrieved data, the stored data anddata from a data source, related to the utility asset; and storing therevised data records for the utility asset in the database.
 12. Themethod of claim 1, wherein the placed RFID tags include a sensor tosense any gas molecule leaks from the utility asset.
 13. The method ofclaim 1, wherein said utility asset is a pipeline and wherein saidsegment tag further includes data describing environmental conditions ofa ditch where the specific segment of the pipeline was buried, and datadescribing a start point and a stop point of a pressure test performedon the specific segment.
 14. A computer implemented method forcapturing, organizing and retrieving data for utility assets using RFIDtags, the method comprising: storing data related to a plurality ofutility assets in a database, wherein the stored data includes dataabout type of the utility assets; repair, documentation, testingvalidation, and inspection of the utility assets; programming aplurality of RFID tags for placement on a utility asset, by one or moreprocessors, wherein said programming comprises: retrieving a unique RFIDtag identifier from a programmed RFID tag using an RFID reader device,linking data associated with the utility asset to the unique RFID tagidentifier, and checking out the programmed RFID tag from an RFIDinventory database by one or more processors; placing the programmedRFID tag on the utility asset; linking stored data related to theutility asset with the programmed data for the placed RFID tag,including location data of the placed RFID tag; and querying the placedRFID tag to retrieve data about the utility asset including data aboutthe location of the utility asset, the type of the utility asset,repair, documentation, testing validation, and inspection of the utilityasset, by one or more processors, wherein said data associated with theutility asset includes stored data describing environmental conditionsincluding soil conditions of a location where the specific segment wasinstalled, and data describing the environmental conditions includingambient temperature at a time when a repair was performed on thespecific segment, and wherein querying one or more of the placed RFIDtags to retrieve data further comprises executing an audit program tovalidate the data or compliance of the data to certain standards. 15.The method of claim 14, wherein at least one of the programmed RFID tagsis placed on a specific segment of the utility asset as a segment tag,and at least one of the programmed RFID tags is placed near a specificjoint of the utility asset as a join tag.
 16. The method of claim 14,further comprising generating a report about the utility asset,according to a plurality of stored rules.
 17. The method of claim 14,wherein said stored data related to the plurality of utility assetsincludes one or more of data collection dates and methods, photographs,voice, videos, and location points, related to the utility asset. 18.The method of claim 14, further comprising programming a repair RFID tagand placing the programmed repair RFID tag on or about a repair area onthe utility asset to describe and validate a repair work performed onthe repair area.
 19. The method of claim 14, wherein said audit programvalidates that all required data and all tag installation rules havebeen followed, according to a plurality of stored business rules. 20.The method of claim 14, further comprising generating a plurality ofrevised data records for the utility asset based on the stored data anddata from a data source, related to the utility asset; and storing therevised data records for the utility asset in the database.